True, this stuff is good. The Co-op does have some good stuff and this is an example of some of it.
inf3rno
Comment 780
True, this stuff is good. The Co-op does have some good stuff and this is an example of some of it.
Hi there Can you please check your dpi on the 24" monitor? xdpyinfo | grep inch it will say something like resolution: 96x96 dots per inch I am reading about font rendering and the importance of setting the right dpi. My monitor is 24" and 1920x1200 too. To check your actual dpi: https://www.sven.de/dpi/ Thanks in advance
This blog is just awesome. Thanks for the beautiful explanation. Looking forward to see more.
Very funny review, thanks!
I've just cleared out my local Asda's store of their stash of Weston's. One "fuck-off 2 litre flagon" :) lasts me about 2 nights and I seem to sleep a lot better too!
Thanks,
This should be sticked on the main page of Gandi SSL Help =)
CORRECTION*
I forgot to add mimetype=plaintext to the URL.
The correct download command for what I explained above is:
sudo wget -O /etc/bind/ad-blacklist 'https://pgl.yoyo.org/adservers/serverlist.php?hostformat=bindconfig;showintro=0;zonefilename=/etc/bind/null.zone.file;mimetype=plaintext'
Thanks.
Actually you do not need to edit the blacklist.
When you download the blacklist you can specify the path to any zone file you want directly into the download URL. Add this to the download URL:
;zonefilename=[path_to_the_file]
For example, if your zone file is at /etc/bind/null.zone.file, you can do like this:
sudo wget -O /etc/bind/ad-blacklist 'https://pgl.yoyo.org/adservers/serverlist.php?hostformat=bindconfig;showintro=0;zonefilename=/etc/bind/null.zone.file'
Also.. the null.zone.file sample file can be downloaded directly at https://pgl.yoyo.org/adservers/null.zone.file
Useful info for those willing to automate the blacklist update process.
Good luck. :)
Thank you.
Thanks, worked like a charm. It still doesn't explain the other failures people observe, which sound quite similar. This is probably related to the lack of proper debugging and lack of usage of kdumps and other low level tools to find these kinds of bugs.
I found your article because I was having the same problem. It ends up being a problem with the SAMBA server. This solved my problem: http://serverfault.com/questions/448987/why-does-samba-with-netbios-aliases-only-load-one-of-the-configurations
I have a similar problem. I have slow samba speeds, about 15MB/s when nautilus mounts with the default GVFS. When I add a CIFS mount to the fstab, I got 85MB/s. I like the speeds, but this have serious drawbacks, you have to maintain the fstab file, you need to add samba passwords to a plain text file, there is no network discovery with it. Is there a GVFS fix? I somehow doubt that changing the NETBIOS name resolution helps, at least I investigated the topic, and the problem appears to be that the GVFS has too small chunks and the chunks size limit is too small.